Release 10.1A: OpenEdge Development:
Programming Interfaces
Building a schema cache file
To build a schema cache file, you use the
SAVECACHEstatement together with a connected database. You must first decide whether you need the entire schema cache or only the schema cache for selected tables of a database. If your application accesses all the tables in the database, you need the complete cache. Otherwise, you can build a schema cache file for only the tables that are accessed by your application.In general, you build a schema cache file off-line, after making a schema change in the database. You can do this in the Procedure Editor directly, or you can write a small maintenance procedure to generate the file.
This is the syntax of the
SAVECACHEstatement:
The
Note: For a DataServer, Progress saves the schema cache for the entire schema holder database. You cannot save the schema cache for a non-OpenEdge database separately. For more information on schema cache files for DataServers, see your OpenEdge DataServer guide.database–namecan be the literal logical name of any OpenEdge database or theVALUE(expression) option, whereexpressionis a character expression that evaluates to the database name.The
pathnamecan be the literal pathname of an operating system file or theVALUE(expression) option, whereexpressionis a character expression that evaluates to the pathname.Saving the entire schema cache
This section describes the steps involved in saving the entire schema cache.
![]()
To save the entire schema cache:
For an example procedure that saves the entire schema cache for one or more databases, see the
SAVECACHEStatement reference entry in the OpenEdge Development: Progress 4GL Reference .Saving a partial schema cache for selected tables
This section describes the steps involved in saving a partial schema cache.
![]()
To save a partial schema cache for selected tables of a database:
|
Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |